Group: Forum Members
Posts: 8.1K,
Visits: 9.4K
|
Thanks, Lee. I can confirm that when SkyDemon saw the ! that I specified be used as a delimited for our protocol extension to feed callsigns through, it reset the "threat level" to unspecified because that ! also triggers our own internal collision detection code. Since that code doesn't run for bearingless targets, I have modified the Flarm parser to not reset the "threat level" you pass when it's a bearingless target. Incidentally, now that you are (presumably) running your own on-device collision detection code (to power your audible alerts) do you also send Flarm protocol alerts through too, and a meaningful "threat level" for positioned targets?
I have also modified the text rendering so it's the same size, and uses the same black-on-yellow glow, as the positioned targets. The position of the text remains unchanged, which is to draw it on the outside of the "circle of probability" in the direction that you are currently travelling.
Paul, we would consider adding a white background behind the traffic details if enough people asked, but my feeling is that it would obscure much more of the map if we did that. When it comes to rendering other traffic we are very mindful of what things will be like when everybody is broadcasting their location (what we ultimately want). I think to have such a solid background, when we get to that wonderful stage, would not be ideal.
|